Techniques for migrating worker nodes to a new manager instance

ABSTRACT

Techniques for migrating worker nodes within clusters to a new manager instance. One technique includes receiving a request to migrate or update a configuration of a cluster within a container system, where the migration or update includes switching from a first communication pathway to a second communication pathway between worker nodes and a manager instance; creating a component and associated IP address for the second communication pathway; communicating a pod specification that includes the IP address for the second communication pathway to the manager instance, where the pod specification will cause a container tool to update each of the worker nodes with the IP address for the second communication pathway; receiving a notification that all worker nodes have been updated with the IP address; and removing a component and associated IP address for the first communication pathway from the cluster.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/456,069, filed Nov. 22, 2021, which claims priority to U.S.Provisional Application No. 63/210,391, filed on Jun. 14, 2021, whichare herein incorporated by reference in their entireties for allpurposes.

FIELD

The present disclosure relates generally to managing containerizedworkloads and services in a virtual cloud network, and moreparticularly, to techniques for migrating worker nodes within clustersto a new manager instance by switching network communications betweenthe worker nodes and various components within a virtual cloud network.

BACKGROUND

Cloud computing providers may manage many compute instances on behalf ofa variety of users. For example, the Oracle Cloud InfrastructureContainer Engine for Kubernetes is a fully-managed, scalable, and highlyavailable service that can be used to deploy containerized applicationsto the cloud. The Container Engine for Kubernetes (OKE) can be used by adevelopment team to build, deploy, and manage cloud-native applications.For example, the development team can specify the compute resources thatapplications require, and the OKE provisions the compute resources onthe Oracle Cloud Infrastructure (OCI) in an existing OCI tenancy. TheOKE uses Kubernetes to provision and manage the compute resources.Kubernetes is an open-source system for automating deployment, scaling,and management of containerized applications across clusters of hosts.Kubernetes groups the containers that make up an application intological units (called pods) for easy management and discovery. Once thecontainerized applications are deployed on the cloud across clusters,the development team can use the OKE to monitor and modify properties ofthe existing clusters such as changing the name of clusters, the numberof node pools in a cluster, a version Kubernetes to run on the controlplane, and enforcement of security policies.

BRIEF SUMMARY

Techniques are provided (e.g., a method, a system, non-transitorycomputer-readable medium storing code or instructions executable by oneor more processors) for migrating worker nodes within clusters to a newmanager instance by switching network communications between the workernodes and various components within a virtual cloud network.

In various embodiments, a computer implemented method is provided thatcomprises: receiving, at a computing system, a request to migrate orupdate a configuration of a cluster within a container system, where themigration or update comprises switching from a first communicationpathway to a second communication pathway between worker nodes and amanager instance; creating, by the computing system, one or morecomponents and associated IP address(es) for the second communicationpathway within the cluster; generating, by the computing system, a podspecification that includes the IP address(es) for the secondcommunication pathway and IP address(es) for the first communicationpathway; communicating, by the computing system, the pod specificationto the manager instance, where the pod specification will cause anapplication programming interface (API) server associated with thecluster to restart with the IP address(es) for the second communicationpathway and the IP address(es) for the first communication pathway, andwhere the restart of the API server will cause a container tool deployedon each of the worker nodes to update each of the worker nodes with theIP address(es) for the second communication pathway; receiving, by thecomputing system, a notification that all worker nodes have been updatedwith the IP address(es) for the second communication pathway; andremoving, by the computing system, one or more components and associatedIP address(es) for the first communication pathway from the cluster.

In some embodiments, the updating each of the worker nodes comprisesiteratively: acquiring, by the container tool, a locking mechanism for aworker node, confirming, by the container tool, connectivity from theworker node to the one or more components and associated IP address(es)for the second communication pathway, updating, by the container tool, aconfiguration file of the worker node to point to the associated IPaddress(es) for the second communication pathway, and releasing, by thecontainer tool, the locking mechanism.

In some embodiments, the updating each of the worker nodes furthercomprises iteratively: updating, by the container tool, a configurationfile of the container tool, restarting the container tool after updatingthe configuration file of the container tool and prior to updating theconfiguration file of the worker node, and clearing a ‘needs-migration’label from the worker node after updating the configuration file of theworker node.

In some embodiments, the notification is received based on clearing the‘needs-migration’ label from all the worker nodes.

In some embodiments, the method further comprises: updating, by thecomputing system, a cluster state of the cluster to include the IPaddress(es) for the second communication pathway; and generating, by thecomputing system based on the cluster state update, certificates thatinclude the IP address(es) for the second communication pathway and IPaddress(es) for the first communication pathway, wherein the podspecification is generated based on the certificates.

In some embodiments, the one or more components for the secondcommunication path comprise a service or software defined virtualnetwork interface card and the one or more components for the firstcommunication pathway comprise a load balancer.

In some embodiments, the method further comprises in response toreceiving the notification that all worker nodes have been updated,scheduling, by the computing system, reclamation of the one or morecomponents and the associated IP address(es) for the first communicationpathway at a predetermine time in the future, wherein the one or morecomponents and associated IP address(es) for the first communicationpathway are removed from the cluster in accordance with the schedulingof reclamation at the predetermine time in the future.

Some embodiments of the present disclosure include a system includingone or more data processors. In some embodiments, the system includes anon-transitory computer readable storage medium containing instructionswhich, when executed on the one or more data processors, cause the oneor more data processors to perform part or all of one or more methodsand/or part or all of one or more processes disclosed herein.

Some embodiments of the present disclosure include a computer-programproduct tangibly embodied in a non-transitory machine-readable storagemedium, including instructions configured to cause one or more dataprocessors to perform part or all of one or more methods and/or part orall of one or more processes disclosed herein.

The techniques described above and below may be implemented in a numberof ways and in a number of contexts. Several example implementations andcontexts are provided with reference to the following figures, asdescribed below in more detail. However, the following implementationsand contexts are but a few of many.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments in accordance with the present disclosure will bedescribed with reference to the drawings, in which:

FIG. 1 illustrates an example environment for migrating or updating acluster configuration according to various embodiments.

FIG. 2 is a flow diagram illustrating a workflow by the control planefor a migration or update of clusters from a first type of clusterconfiguration to a second type of cluster configuration according tovarious embodiments.

FIG. 3 is a flow diagram illustrating a workflow by the management planefor a migration or update of clusters from a first type of clusterconfiguration to a second type of cluster configuration according tovarious embodiments.

FIG. 4 is a flow diagram illustrating a workflow by the container toolfor a migration or update of clusters from a first type of clusterconfiguration to a second type of cluster configuration according tovarious embodiments.

FIG. 5 is a flow diagram illustrating a workflow by the scheduler for amigration or update of clusters from a first type of clusterconfiguration to a second type of cluster configuration according tovarious embodiments.

FIG. 6 is a block diagram illustrating one pattern for implementing acloud infrastructure as a service system, according to at least oneembodiment.

FIG. 7 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 8 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 9 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 10 is a block diagram illustrating an example computer system,according to at least one embodiment.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofcertain embodiments. However, it will be apparent that variousembodiments may be practiced without these specific details.Furthermore, well-known features may be omitted or simplified in ordernot to obscure the embodiment being described. The figures anddescription are not intended to be restrictive. The word “exemplary” isused herein to mean “serving as an example, instance, or illustration.”Any embodiment or design described herein as “exemplary” is notnecessarily to be construed as preferred or advantageous over otherembodiments or designs.

Introduction

In a virtual cloud network, the migration or update of clusters from onetype of cluster configuration to another type of cluster configurationtypically involves switching the network communication betweencomponents (e.g., between the clusters' manager instance and workernodes). For example, the migration or update of clusters from aconfiguration of V1Hardened (hardened clusters with worker nodes on acustomer's tenancy connected via a load balancer to a manager instanceon a service tenancy) to configuration of V2 Native VCN Clusters(clusters with worker nodes on a customer's tenancy connected viaservice or software defined virtual network interface cards (SVNIC) to amanager instance on a service tenancy) may involve switching the networkcommunication between the cluster's Kubernetes manager instance (KMI)and its worker nodes off of the Load Balancer and onto a new SVNIC. TheSVNIC may be created in the customer's tenancy and attached to thecustomer specified subnet, and may be connected to the KMI on theservice tenancy by a microVNIC. Communication between the KMI and theworker nodes may be on private Internet Protocol (IP) addresses throughthe SVNIC, but the SVNIC may support a public IP address that thecustomer can optionally request and use. The result of this exemplarymigration would be increased security and improved resource utilization.

However, it is difficult for service providers to implement a migrationor update (e.g., migrating from an initial version of a KMI to asubsequent version of a KMI) seamlessly on a preexisting containersystem such as Kubernetes without disrupting the customer's services. Inmany instances (e.g., an Infrastructure-as-a-Service (IaaS) system orany cloud computing service), the various components of the preexistingcontainer system such as Kubernetes are deployed across multipletenancies, for example, the service provider's tenancy and thecustomer's tenancy. As used herein, multi-tenancy means that a singleinstance of the software and its supporting infrastructure servesmultiple tenants. Each tenant shares software applications and may alsoshare real and virtual hardware such as managers, databases, etc. Eachtenant's data is isolated and remains invisible to other tenants (eventhe service provider tenancy). Thus, the cloud service providertypically does not have direct access to components of the containersystem (e.g., worker nodes) within the customer tenancy, which creates aproblem when the service provider migrates or updates components withintheir tenancy that affect components within the customer tenancy. Theservice provider needs an approach to implement a migration or update ofthe various components within the container system (including thosewithin the customer tenancy) without direct access and withoutdisrupting the customer's services.

To overcome these challenges and others, various embodiments aredirected to techniques for migrating or updating of clusters from onetype of cluster configuration to another type of cluster configuration.The techniques described in detail herein pertain to modifying and usingexisting components of the container system (e.g., a container tool suchas a DaemonSet) and the virtual cloud network (e.g., connectivitybetween the service tenancy and the client tenancy via the containertool and container engine) to disconnect and connect various componentsof the container system in order to migrate or update configurations. Inan exemplary embodiment, a technique implemented by a computing systemfor the migration or update of clusters from a first type of clusterconfiguration to a second type of cluster configuration includes:receiving, at a computing system, a request to migrate or update aconfiguration of a cluster within a container system, where themigration or update comprises switching from a first communicationpathway to a second communication pathway between worker nodes and amanager instance; creating, by the computing system, one or morecomponents and associated IP address(es) for the second communicationpathway within the cluster; generating, by the computing system, a podspecification that includes the IP address(es) for the secondcommunication pathway and IP address(es) for the first communicationpathway; communicating, by the computing system, the pod specificationto the manager instance, where the pod specification will cause anapplication programming interface (API) server associated with thecluster to restart with the IP address(es) for the second communicationpathway and the IP address(es) for the first communication pathway, andwhere the restart of the API server will cause a container tool deployedon each of the worker nodes to update each of the worker nodes with theIP address(es) for the second communication pathway; receiving, by thecomputing system, a notification that all worker nodes have been updatedwith the IP address(es) for the second communication pathway; andremoving, by the computing system, one or more components and associatedIP address(es) for the first communication pathway from the cluster.

Computing System For Migrating or Updating Cluster Components

FIG. 1 is a block diagram illustrating a computing environment 100 formigrating worker nodes within clusters to a new manager instance byswitching network communications between the worker nodes and variouscomponents within a virtual cloud network. However, it should beunderstood that a similar computing environment can be implemented formigrating or updating clusters from any type of cluster configuration toany other type of cluster configuration. Especially those clusterconfigurations where various components of the preexisting containersystem are deployed across multiple tenancies. As shown in FIG. 1 , thecomputing environment 100 includes a service tenancy 105 (e.g., aservice provider's tenancy such as the OKE) and a customer tenancy 110.The service tenancy 105 includes a control plane 115, a management plane120, and a KMI 125. The customer tenancy 110 includes worker nodes 130.

The control plane 115 is the part of the software that configures andcontrols a data plane including the management plane 120 and the KMI125. For example, the control plane 115 may be used for adding,updating, and removing components (e.g., in terms of a containersystem—creation of nodes, managers, and policies governing users access)on the data plane. The management plane 120 is the part of the softwarethat processes the data requests (e.g., implements migrations, updates,business logic, etc.). For example, the management plane 125 takes thenodes, managers, and policies, and implements migration, updates,business logic, etc. on top of them (e.g., updating manager instances).The KMI 125 is one or more manager instances which run the containersystem control plane (e.g., the Kubernetes control plane) components fora dedicated cluster. Each cluster may have multiple KMIs 125, whichprovide high availability. A cluster comprises a set of worker machines,called worker nodes 130, that run containerized applications. Everycluster has at least one worker node 130. With respect specifically toKubernetes, the worker node(s) 130 host Pods that are the components ofthe application workload. A Pod is a Kubernetes abstraction thatrepresents a group of one or more application containers (such asDocker), and some shared resources for those containers. Those resourcesmay include: shared storage, as volumes, networking, as a unique clusterIP address, and information about how to run each container, such as thecontainer image version or specific ports to use. The Kubernetes controlplane manages the worker nodes 130 and the Pods in the cluster. Inproduction environments, the Kubernetes control plane usually runsacross multiple computers or virtual machines and a cluster usually runsmultiple worker nodes 130, providing fault-tolerance and highavailability.

As illustrated in FIG. 1 , in a first cluster configuration (hereincalled V1 or V1Hardened) the worker nodes 130 are connected to the KMI125 via an old version communication path 135 that includes loadbalancers 140 residing on the service tenancy 105. The service provideris interested migrating or updating the cluster to a second clusterconfiguration (herein called V2 or V2 Native VCN Clusters) in order toget communication between the worker nodes 130 and the KMI 125 off ofthe load balancers 140 in the service tenancy 105, and on to SVNICs 145in the customer tenancy 110 via an new version communication path 147.In or order to implement this migration or update, the customerinitiates a V2 migration by making an API call to the control plane 115and passing in the required information, including the ID of thecustomer's subnet where the SVNIC 145 should be attached, and whetherthe customer would like a public IP address to be created and attachedto the SVNIC 145 as well, and the ID of network security groups thecustomer would like applied. The control plane 115 will add a V2migration request that the V2 migration nanny will pick up and use tospawn a V2 migration workflow (discussed in detail herein). The controlplane 115V2 migration workflow will validate the input and the clusterstate, create the SVNIC 145 and optional public IP, and attach the SVNIC145. Up until this point, if there is a failure, the cluster can stillbe rolled back to the original state, but starting with the next step,there may be no rollback. The next step is for control plane 115 toupdate the cluster state in a messaging application programminginterface (MAPI), using the private IP address of the new SVNIC 145 asthe advertise address, and including the existing load balancer 140public IP and the optional SVNIC public IP in the additional addresses.After the control plane 115 confirms that the management plane 120 wasable to reconcile the change, the control plane 115 will delete the oldSVNIC from the customer tenancy 110 that each V1H cluster uses tocommunicate to OCI Services via the KMI 125. In V2 clusters, KMI's 125communicate to OCI Services via a service gateway configured in thecustomers network.

When the control plane 115, updates the state of the cluster by callingMAPI, the management plane 120 may reconcile the change and take severalactions including attaching a new muNIC or microVNIC 150 associated withthe new SVNIC 145. The detailed flow may be as follows: the managementplane 120 MP3 may generate new certificates for the KMI's 125 thatinclude both the load balancer 140 public IP address and the SVNIC's 145address(es). So the customer can continue to reach the kube-api-serverusing either the old or the new addresses. The Proxymux server will alsoget a new certificate that includes the load balancer 140 public IPaddress and the SVNIC's 145 address(es). The management plane 120 willcreate a new pod spec, and push it to the KMIs 125. All of thecontainers will be restarted, kubet-api-server will restart with the newadvertised address(es). The control plane 115 will poll for thisreconciliation to be complete, and if it completes successfully, willconsider the migration workflow to have completed successfully, and willupdate the V2 Migration Complete timestamp for the cluster to thecurrent time.

In the meantime, on each of the worker nodes 130 in the cluster, aproxymux client 155 resides that will be watching for changes inendpoint of the kubernetes.default 160 service that will be triggered bythe kube-api-server restarting with the new advertise address(es). Whenproxymux client 155 sees this value change, it will start its migrationsequence, but only after it sees that the advertise address(es) hassettled down to a single address. As the kube-api-servers are restartingat different times, there will be a time when different kube-api-serversare advertising different addresses. Proxymux client 155 will wait forthis to quiesce back to a single address before proceeding.

The proxymux client 155 migration sequence will be comprised ofacquiring a configmap lock, so that only one worker node 130 in thecluster will attempt the migration at a time. Proxymux client 155 willconfirm that connectivity (e.g., tcp connectivity) to the new address isworking properly. If it is, proxymux client 155 will change the proxymuxserver address in its config and restart. Proxymux client 155 will thenupdate the worker node's 130 kubeconfig 165(/etc/kubernetes/kubelet.conf) to point to the server at the newaddress. The kubelet service definition in systemd will also need to beupdated so that pods don't get restarted when kubelet is restarted.

If the proxymux client 155 is not able to verify connectivity via thenew address, the proxymux client 155 will halt the migration and theneedsMigration label will not get updated. This will indicate that themigration was blocked by a network connectivity error. This error may bethe result of customer misconfiguration of the network, and may beremediated by the customer. The proxymux client 155 will continue toperiodically test the connectivity, so after the customer has fixed thenetwork configuration, the proxymux client migration will resumeautomatically. After the proxymux client 155 has successfully migrated aworker node 130 to use the new IP address, the proxymux client 155 willclear the ‘needs-migration’ label from the worker node 130. It will waita predetermined amount of time (e.g., 40 seconds) before releasing thelease. This will allow proxymux clients 155 running on other workernodes 130 to attempt migration on their worker nodes 130.

At this point, all OKE/Kubernetes communication will be configured touse the private IP address of the SVNIC 145, and it will be up to thecustomer to update all of their references from the old load balancer's140 public IP address to the new SVNIC address. This could be the SVNICprivate IP address, or the optional SVNIC public IP address, accordingto the customer's configuration. To do this, the customer will have tocall CreateKubeConfig file on the migrated cluster, to get a kubeconfig165 that has all the endpoints and manually select the SVNIC server outof it. The load balancer public IP may be listed first, so the customermay also have to specify the server to be the SVNIC IP after they'veupdated the kubeconfig 165. If they don't update that, they won'tactually be exercising the new network path and could mask networkissues until the reclamation workflow comes along later and removes theload balancer. Even if there aren't network issues, if the customerdoesn't specify the SVNIC as the server, they could experienceinterruption when the load balancer is deleted.

By default, the customer will have a predetermined number of days (e.g.,30 days) to make this transition. After this grace period has expired,the control plane 115 will attempt to reclaim the load balancer 140 andits associated public IP address. The customer will also have theability to file a ticket to request an extension to their grace period.A second attribute of the cluster called reclamationExtension will beused for an override of the migration completion and grace periodcalculation. To grant the customer an extension, an operator would needto update that value to a new date indicating when the grace period willexpire. This field can also be used to decrease the grace period bysetting it to a value less than the migration completion date anddefault grace period.

A nanny workflow will be responsible for scanning clusters to find onewith a V2MigrationComplete timestamp that is set, and whose value ismore than the predetermined number of day (e.g., 30*days) in the past,and don't have a reclamationExtension timestamp set to a future date.Clusters meeting these criteria will have reclamation workflows createdfor them. The reclamation workflow will make a call to MAPI to fetch thelabels for the worker nodes 130 in the cluster. It will check to makesure that none of the worker nodes 130 have a ‘needs-migration’ labelwith a value that indicates that the proxymux migration was notcomplete. If the workflow cannot progress due to this condition, it willupdate the reclamationExtension timestamp attribute for the cluster byadding an additional predetermined number of days (e.g., 10*days), andthe workflow will fail. This will give an opportunity to contact thecustomer to let them know that their migration has not completedsuccessfully. The work of the reclamation workflow will be to update theclusterState to remove the load balancer's 140 IP address from the listof endpoints, wait for that to be reconciled, then delete the DNS recordassociated with the load balancer if it exists (some legacy V1 clustersmay have had DNS records created automatically for the load balancerpublic ip), and finally to delete the load balancer 140 itself.

Techniques For Migrating or Updating Cluster Components

FIGS. 2-5 illustrate processes and operations for making eventualconsistency cache updates deterministic. Individual embodiments may bedescribed as a process which is depicted as a flowchart, a flow diagram,a data flow diagram, a structure diagram, or a block diagram. Although aflowchart may describe the operations as a sequential process, many ofthe operations may be performed in parallel or concurrently. Inaddition, the order of the operations may be re-arranged. A process isterminated when its operations are completed, but could have additionalsteps not included in a figure. A process may correspond to a method, afunction, a procedure, a subroutine, a subprogram, etc. When a processcorresponds to a function, its termination may correspond to a return ofthe function to the calling function or the main function.

The processes and/or operations depicted in FIGS. 2-5 may be implementedin software (e.g., code, instructions, program) executed by one or moreprocessing units (e.g., processors cores), hardware, or combinationsthereof. The software may be stored in a memory (e.g., on a memorydevice, on a non-transitory computer-readable storage medium). Theparticular series of processing steps in FIGS. 2-5 is not intended to belimiting. Other sequences of steps may also be performed according toalternative embodiments. For example, in alternative embodiments thesteps outlined above may be performed in a different order. Moreover,the individual steps illustrated in FIGS. 2-5 may include multiplesub-steps that may be performed in various sequences as appropriate tothe individual step. Furthermore, additional steps may be added orremoved depending on the particular applications. One of ordinary skillin the art would recognize many variations, modifications, andalternatives.

FIG. 2 shows a flowchart 200 that illustrates a workflow by the controlplane for a migration or update of clusters from a first type of clusterconfiguration to a second type of cluster configuration. The processesdepicted in the flowchart 200 may be implemented by the architecture,systems, and techniques depicted in FIGS. 1 and 6-10 . At step 205, themigration or update of clusters from a first type of clusterconfiguration to a second type of cluster configuration is initiated.The process may be initiated by a customer submitting a request withcustomer information for migration or update of clusters from a firsttype of cluster configuration to a second type of cluster configuration.The migration or update may be defined by the service provide, thecustomer, or a combination thereof. In some instances, the migration orupdate comprises removing current component(s) of the first type ofcluster configuration (also referred to herein as old components orfirst version components (V1)), adding updated component(s) of thesecond type of cluster configuration (also referred to herein as newcomponents or second version components (V2)), changing paths ofcommunication or networking (e.g., changing IP addresses), or anycombination thereof. At step 210, check to see if a cluster identifiedby the request has a first type of cluster configuration. If it doesnot, end process or start workflow for migrating or updating a differenttype of cluster configuration. At step 215, the customer information inthe request is validated. The customer information may include the ID ofthe customer's subnet where the updated component(s) of the second typeof cluster configuration should be attached.

At step 220, the one or more updated components (e.g., a SVNIC) of thesecond type of cluster configuration are created. In some instances, theone or more updated components are created with a private IP address.The creating may include waiting for the component to come online anddemonstrate connectivity, for example, via the private IP address.Optionally, the one or more components are created with a public IPaddress. The creating may include waiting for the one or more updatedcomponents to come online and demonstrate connectivity, for example, viathe private and/or the public IP address. The creating may furtherinclude adding attachments for the one or more updated components (withprivate and/or public IP addresses), and waiting for the attachments tocome online and demonstrate connectivity, for example, via the privateand/or the public IP address. At step 225, secrets (e.g., Secrets inVault—SiV) are uploaded. In various instances, prior to this point atstep 220, failure cases will rollback the migration or update.Subsequent to this point at step 220, failure cases will result in thecluster being stuck in migration or updating, and no rollback ispossible.

At step 230, the cluster state is updated in the MAPI. In someinstances, the update includes the IP address(es) of the newly createdone or more updated components (e.g., SVNIC) as well as the IPaddress(es) of one or more current or previous version components beingreplaced (e.g., load balancers). This step triggers the certificategeneration (e.g., KMI/proxymux certificates) by the management plane andcauses the manager instances (e.g., KMI) to stop using the one or morecurrent or previous version components being replaced for cloud serviceconnectivity such as OCI Service connectivity. Once updated, the controlplane waits for the management plane to complete its workflow (see FIG.3 ). While waiting, the control plane may poll for reconciliation. Forexample, changes to and by the container tool on worker nodes of acluster (e.g., a DaemonSet referred to herein as a proxymux createdautomatically by the OKE on worker nodes during deployment) can takeseveral hours. Therefore, the control plane may using polling and‘needs-migration’ labels outside of this workflow to determineprogress/success of the migration or update within the cluster. At step235, once the migration or update for the cluster is completed orsuccessful, a database or data table (e.g., kiev) may be updated. Forexample, a timestamp in a database or data table maybe updated to thecurrent time/date, to indicate that the migration or update is completedor successful for the cluster and the reclamation scheduler may create aworkflow for the cluster in the future (see FIG. 5 ).

FIG. 3 shows a flowchart 300 that illustrates a workflow of themanagement plane for a migration or update of clusters from a first typeof cluster configuration to a second type of cluster configuration. Theprocesses depicted in the flowchart 300 may be implemented by thearchitecture, systems, and techniques depicted in FIGS. 1 and 6-10 . Atstep 305, the changes from the control plane (e.g., the changes in IPaddresses and components) are reconciled. In other words, this stepinitiates the processes to make the changes instructed by the controlplane to migrate or update the clusters from the first type of clusterconfiguration to the second type of cluster configuration. At step 310,one or more additional components (e.g., a new muNIC associated to thenew SVNIC) for the second type of cluster configuration are created. Insome instances, the one or more additional components are created with aprivate IP address. The creating may include waiting for the componentto come online and demonstrate connectivity, for example, via theprivate IP address. The creating may further include adding attachmentsfor the one or more additional components (with private IP addresses),and waiting for the attachments to come online and demonstrateconnectivity, for example, via the private IP address.

At step 315, new certificates are generated for the manager instancesthat include the IP address(es) for the one or more current or previousversion components (e.g., load balancer) to be removed from the clusterconfiguration and the IP address(es) for the one or more new components(e.g., SVNIC) to be added to the cluster configuration. This allows forthe cluster to continue to reach the API server (e.g., Kubernetes APIserver—kube-api-server) using either the old or the new addresses. TheAPI server validates and configures data for the API objects whichinclude pods, services, replication controllers, and others. The APIserver services REST operations and provides the frontend to thecluster's shared state through which all other components interact. Atstep 320, new pod specifications are generated comprising the newcertificates, and the new pod specifications are pushed to the managerinstances advertising the new IP address(es), which causes the APIserver to restart with the new advertised IP address(es).

FIG. 4 shows a flowchart 400 that illustrates a workflow of the workernodes (specifically the container tool such as proxymux on each workernode) for a migration or update of clusters from a first type of clusterconfiguration to a second type of cluster configuration. The processesdepicted in the flowchart 400 may be implemented by the architecture,systems, and techniques depicted in FIGS. 1 and 6-10 . At step 405, APIservers will be restarted with the advertised IP address(es) set to thenew IP address(es) for the one or more new components (e.g., SVNIC) tobe added to the cluster configuration (e.g.,kube-api-server—advertise-address) causing the IP address of the workernode cluster service (e.g., kubernetes.default service) to change. Eachcluster is provisioned with a cluster service that provides a way forinternal applications to talk to the API server. Essentially, thecluster service can be used to easily expose an application deployed ona set of pods using a single endpoint. At step 410, the container toolsuch as proxymux each worker node will detect the change in IP addressand determine if the configuration files for the cluster (e.g., thekubeconfig and proxymux config) need to be updated. A file that is usedto configure access to a cluster is sometimes called a kubeconfig file.This is a generic way of referring to configuration files. A file thatis used to configure the container tool is sometimes called a proxymuxconfig file. When the container tool determines the configuration filesof the worker node need to be updated, each container tool will attemptto obtain a locking mechanism such as configmap lock to lock therespective worker node for the configuration update. Configmap is an APIobject used to store non-confidential data in key-value pairs. Pods canconsume configmaps as environment variables, command-line arguments, oras configuration files in a volume. The locking mechanism is onlyobtainable by one container tool at a time thus ensuring only one workernode at a time is being updated. If the container tool is unable toacquire the configmap lock, either due to a network connectivity issue,or due to another node owning the locking mechanism, it will retry withbackoff (i.e., waits for an amount of time before attempting toretransmit).

At step 415, the container tool that has the configmap lock will ensureconnectivity (e.g., TCP connectivity) to API server via the advertisedaddress (e.g., the component private IP address). In the event that thecontainer tool is not able to verify the connectivity to the new IPaddress, the container tool will retry with backoff, so that once thenetwork configuration is resolved, the container tool can resumemigration. In order for the container tool to be able to make in-clustercalls, it will use a service account with a rolebinding created by themanagement plane. Once connectivity is ensured to the API server, atstep 420 the container tool updates the container tool configurationfiles and restarts the container tool. The container tool will alsoupdate the server address in other configuration files such askubeconfig and restart the node agent (e.g., kubelet that runs on eachworker node). The node agent can register the worker node with the APIserver. In some instances, the container tool will also clear the‘needs-migration’ label from the worker node. In additional oralternative instances, the container tool will generate and communicatea metric to the management plane showing the worker node has beenmigrated.

FIG. 5 shows a flowchart 500 that illustrates a workflow of thereclamation scheduler nanny for a migration or update of clusters from afirst type of cluster configuration to a second type of clusterconfiguration. The processes depicted in the flowchart 500 may beimplemented by the architecture, systems, and techniques depicted inFIGS. 1 and 6-10 . The reclamation scheduler nanny provides the abilityto schedule reclamations for clusters that have exceeded their graceperiod, while also providing the ability to tune how many reclamationworkflows are outstanding at any given time. The nanny schedulesaccording to the order of the V2MigrationComplete orreclamationExtension time (if it is set), and does not take into accountprevious reclamation workflow failures for a cluster. Scheduling isbased on the V2MigrationComplete timestamp. When this value is set, andis set to more than a certain number of days in the past, the clustermay be eligible for reclamation. The number of days past, referred to asthe reclamation grace period is defaulted to a predetermined number ofdays (e.g., 30 days), but will be stored in storage device (e.g.,Spectre) so that it is configurable and overridable. Each cluster willalso have a field called reclamationExtension. This field will normallybe unset, but a customer can request an extension to their reclamationgrace period by filing a ticket. If the request is granted, thereclamationExtension timestamp will be set as an override to the (e.g.,V2MigrationComplete+30*days) requirement. The reclamationExtension willmark the last day of the extension directly, not n−30 days, since the 30is variable. The reclamationExtension can be set to a date less than(V2MigrationComplete+30*days) for customers that don't want to wait thefull grace period for the reclamation to occur. The customer can file aticket to request an extension to their grace period. This request canbe satisfied by having an operator update the timestamp value ofreclamationExtension on the cluster.

Part of the reclamation workflow will check to see if any of the nodesstill have the ‘needs-migration’ label. If there are none, thereclamation will proceed. If some or all of the nodes still have thatlabel, operations fall into the section of the workflow called ‘MaximumReclamation Grace Period’. At step 505, the scheduler confirms proxymuxmigration has completed by checking the worker nodes in the cluster forthe ‘needs-migration’ label. Once the scheduler confirms proxymuxmigration has completed for all worker nodes on the cluster, at step 510the scheduler updates MAPI to remove the IP address(es) for the one ormore current or previous version components (e.g., load balancer) fromthe endpoint. The scheduler may then wait for the management plane toreconcile the update of the MAPI. Once reconciled, at step 515 thescheduler will delete the DNS record (if one exists) associated with theIP address(es) for the one or more current or previous versioncomponents (e.g., load balancer). At step 520, the scheduler will deletethe one or more current or previous version components from the clusterconfiguration.

If any step after step 505 fails, the workflow will stop without rollingback and the workflow will be marked failed. This will allow thereclamation workflow to be rescheduled, and tried again automatically.For this reason, all steps must be tolerant of attempting to deleteresources that have already been deleted. If the reclamation workflowfails because of the ‘needs-migration’ label check, it will set thereclamationExtension to a date in the future. How far into the futurewill be configured as a storage device (e.g., Spectre) value whosedefault is a predetermined number of days (e.g., 10 days). This willprevent the same cluster from getting scheduled over and over. Theworkflow failure will trigger an alarm that will give the serviceprovider the opportunity to reach out to the customer to notify themthat their network configuration is incorrect and their migration didnot complete.

For most cases, reclamation will not proceed on a cluster where one ormore nodes still have the ‘needs-migration’ label set. However, there isa need to decide how to handle clusters that have been in this state fora very long time, and for clusters where the majority of nodes havemigrated successfully. This is known as Maximum Reclamation GracePeriod. Having two fields, the V2MigrationComplete timestamp and thereclamationExtension timestamp will allow the service provider to definea policy of maximum amount of extensions.

As noted above, infrastructure as a service (IaaS) is one particulartype of cloud computing. IaaS can be configured to provide virtualizedcomputing resources over a public network (e.g., the Internet). In anIaaS model, a cloud computing provider can host the infrastructurecomponents (e.g., servers, storage devices, network nodes (e.g.,hardware), deployment software, platform virtualization (e.g., ahypervisor layer), or the like). In some cases, an IaaS provider mayalso supply a variety of services to accompany those infrastructurecomponents (e.g., billing, monitoring, logging, load balancing andclustering, etc.). Thus, as these services may be policy-driven, IaaSusers may be able to implement policies to drive load balancing tomaintain application availability and performance.

In some instances, IaaS customers may access resources and servicesthrough a wide area network (WAN), such as the Internet, and can use thecloud provider's services to install the remaining elements of anapplication stack. For example, the user can log in to the IaaS platformto create virtual machines (VMs), install operating systems (OSs) oneach VM, deploy middleware such as databases, create storage buckets forworkloads and backups, and even install enterprise software into thatVM. Customers can then use the provider's services to perform variousfunctions, including balancing network traffic, troubleshootingapplication issues, monitoring performance, managing disaster recovery,etc.

In most cases, a cloud computing model will require the participation ofa cloud provider. The cloud provider may, but need not be, a third-partyservice that specializes in providing (e.g., offering, renting, selling)IaaS. An entity might also opt to deploy a private cloud, becoming itsown provider of infrastructure services.

In some examples, IaaS deployment is the process of putting a newapplication, or a new version of an application, onto a preparedapplication server or the like. It may also include the process ofpreparing the server (e.g., installing libraries, daemons, etc.). Thisis often managed by the cloud provider, below the hypervisor layer(e.g., the servers, storage, network hardware, and virtualization).Thus, the customer may be responsible for handling (OS), middleware,and/or application deployment (e.g., on self-service virtual machines(e.g., that can be spun up on demand) or the like.

In some examples, IaaS provisioning may refer to acquiring computers orvirtual hosts for use, and even installing needed libraries or serviceson them. In most cases, deployment does not include provisioning, andthe provisioning may need to be performed first.

In some cases, there are two different challenges for IaaS provisioning.First, there is the initial challenge of provisioning the initial set ofinfrastructure before anything is running. Second, there is thechallenge of evolving the existing infrastructure (e.g., adding newservices, changing services, removing services, etc.) once everythinghas been provisioned. In some cases, these two challenges may beaddressed by enabling the configuration of the infrastructure to bedefined declaratively. In other words, the infrastructure (e.g., whatcomponents are needed and how they interact) can be defined by one ormore configuration files. Thus, the overall topology of theinfrastructure (e.g., what resources depend on which, and how they eachwork together) can be described declaratively. In some instances, oncethe topology is defined, a workflow can be generated that creates and/ormanages the different components described in the configuration files.

In some examples, an infrastructure may have many interconnectedelements. For example, there may be one or more virtual private clouds(VPCs) (e.g., a potentially on-demand pool of configurable and/or sharedcomputing resources), also known as a core network. In some examples,there may also be one or more inbound/outbound traffic group rulesprovisioned to define how the inbound and/or outbound traffic of thenetwork will be set up and one or more virtual machines (VMs). Otherinfrastructure elements may also be provisioned, such as a loadbalancer, a database, or the like. As more and more infrastructureelements are desired and/or added, the infrastructure may incrementallyevolve.

In some instances, continuous deployment techniques may be employed toenable deployment of infrastructure code across various virtualcomputing environments. Additionally, the described techniques canenable infrastructure management within these environments. In someexamples, service teams can write code that is desired to be deployed toone or more, but often many, different production environments (e.g.,across various different geographic locations, sometimes spanning theentire world). However, in some examples, the infrastructure on whichthe code will be deployed must first be set up. In some instances, theprovisioning can be done manually, a provisioning tool may be utilizedto provision the resources, and/or deployment tools may be utilized todeploy the code once the infrastructure is provisioned.

FIG. 6 is a block diagram 600 illustrating an example pattern of an IaaSarchitecture, according to at least one embodiment. Service operators602 can be communicatively coupled to a secure host tenancy 604 that caninclude a virtual cloud network (VCN) 606 and a secure host subnet 608.In some examples, the service operators 602 may be using one or moreclient computing devices, which may be portable handheld devices (e.g.,an iPhone®, cellular telephone, an iPad®, computing tablet, a personaldigital assistant (PDA)) or wearable devices (e.g., a Google Glass® headmounted display), running software such as Microsoft Windows Mobile®,and/or a variety of mobile operating systems such as iOS, Windows Phone,Android, BlackBerry 8, Palm OS, and the like, and being Internet,e-mail, short message service (SMS), Blackberry®, or other communicationprotocol enabled. Alternatively, the client computing devices can begeneral purpose personal computers including, by way of example,personal computers and/or laptop computers running various versions ofMicrosoft Windows®, Apple Macintosh®, and/or Linux operating systems.The client computing devices can be workstation computers running any ofa variety of commercially-available UNIX® or UNIX-like operatingsystems, including without limitation the variety of GNU/Linux operatingsystems, such as for example, Google Chrome OS. Alternatively, or inaddition, client computing devices may be any other electronic device,such as a thin-client computer, an Internet-enabled gaming system (e.g.,a Microsoft Xbox gaming console with or without a Kinect® gesture inputdevice), and/or a personal messaging device, capable of communicatingover a network that can access the VCN 606 and/or the Internet.

The VCN 606 can include a local peering gateway (LPG) 610 that can becommunicatively coupled to a secure shell (SSH) VCN 612 via an LPG 610contained in the SSH VCN 612. The SSH VCN 612 can include an SSH subnet614, and the SSH VCN 612 can be communicatively coupled to a controlplane VCN 616 via the LPG 610 contained in the control plane VCN 616.Also, the SSH VCN 612 can be communicatively coupled to a data plane VCN618 via an LPG 610. The control plane VCN 616 and the data plane VCN 618can be contained in a service tenancy 619 that can be owned and/oroperated by the IaaS provider.

The control plane VCN 616 can include a control plane demilitarized zone(DMZ) tier 620 that acts as a perimeter network (e.g., portions of acorporate network between the corporate intranet and external networks).The DMZ-based servers may have restricted responsibilities and help keepbreaches contained. Additionally, the DMZ tier 620 can include one ormore load balancer (LB) subnet(s) 622, a control plane app tier 624 thatcan include app subnet(s) 626, a control plane data tier 628 that caninclude database (DB) subnet(s) 630 (e.g., frontend DB subnet(s) and/orbackend DB subnet(s)). The LB subnet(s) 622 contained in the controlplane DMZ tier 620 can be communicatively coupled to the app subnet(s)626 contained in the control plane app tier 624 and an Internet gateway634 that can be contained in the control plane VCN 616, and the appsubnet(s) 626 can be communicatively coupled to the DB subnet(s) 630contained in the control plane data tier 628 and a service gateway 636and a network address translation (NAT) gateway 638. The control planeVCN 616 can include the service gateway 636 and the NAT gateway 638.

The control plane VCN 616 can include a data plane mirror app tier 640that can include app subnet(s) 626. The app subnet(s) 626 contained inthe data plane mirror app tier 640 can include a virtual networkinterface controller (VNIC) 642 that can execute a compute instance 644.The compute instance 644 can communicatively couple the app subnet(s)626 of the data plane mirror app tier 640 to app subnet(s) 626 that canbe contained in a data plane app tier 646.

The data plane VCN 618 can include the data plane app tier 646, a dataplane DMZ tier 648, and a data plane data tier 650. The data plane DMZtier 648 can include LB subnet(s) 622 that can be communicativelycoupled to the app subnet(s) 626 of the data plane app tier 646 and theInternet gateway 634 of the data plane VCN 618. The app subnet(s) 626can be communicatively coupled to the service gateway 636 of the dataplane VCN 618 and the NAT gateway 638 of the data plane VCN 618. Thedata plane data tier 650 can also include the DB subnet(s) 630 that canbe communicatively coupled to the app subnet(s) 626 of the data planeapp tier 646.

The Internet gateway 634 of the control plane VCN 616 and of the dataplane VCN 618 can be communicatively coupled to a metadata managementservice 652 that can be communicatively coupled to public Internet 654.Public Internet 654 can be communicatively coupled to the NAT gateway638 of the control plane VCN 616 and of the data plane VCN 618. Theservice gateway 636 of the control plane VCN 616 and of the data planeVCN 618 can be communicatively couple to cloud services 656.

In some examples, the service gateway 636 of the control plane VCN 616or of the data plane VCN 618 can make application programming interface(API) calls to cloud services 656 without going through public Internet654. The API calls to cloud services 656 from the service gateway 636can be one-way: the service gateway 636 can make API calls to cloudservices 656, and cloud services 656 can send requested data to theservice gateway 636. But, cloud services 656 may not initiate API callsto the service gateway 636.

In some examples, the secure host tenancy 604 can be directly connectedto the service tenancy 619, which may be otherwise isolated. The securehost subnet 608 can communicate with the SSH subnet 614 through an LPG610 that may enable two-way communication over an otherwise isolatedsystem. Connecting the secure host subnet 608 to the SSH subnet 614 maygive the secure host subnet 608 access to other entities within theservice tenancy 619.

The control plane VCN 616 may allow users of the service tenancy 619 toset up or otherwise provision desired resources. Desired resourcesprovisioned in the control plane VCN 616 may be deployed or otherwiseused in the data plane VCN 618. In some examples, the control plane VCN616 can be isolated from the data plane VCN 618, and the data planemirror app tier 640 of the control plane VCN 616 can communicate withthe data plane app tier 646 of the data plane VCN 618 via VNICs 642 thatcan be contained in the data plane mirror app tier 640 and the dataplane app tier 646.

In some examples, users of the system, or customers, can make requests,for example create, read, update, or delete (CRUD) operations, throughpublic Internet 654 that can communicate the requests to the metadatamanagement service 652. The metadata management service 652 cancommunicate the request to the control plane VCN 616 through theInternet gateway 634. The request can be received by the LB subnet(s)622 contained in the control plane DMZ tier 620. The LB subnet(s) 622may determine that the request is valid, and in response to thisdetermination, the LB subnet(s) 622 can transmit the request to appsubnet(s) 626 contained in the control plane app tier 624. If therequest is validated and requires a call to public Internet 654, thecall to public Internet 654 may be transmitted to the NAT gateway 638that can make the call to public Internet 654. Memory that may bedesired to be stored by the request can be stored in the DB subnet(s)630.

In some examples, the data plane mirror app tier 640 can facilitatedirect communication between the control plane VCN 616 and the dataplane VCN 618. For example, changes, updates, or other suitablemodifications to configuration may be desired to be applied to theresources contained in the data plane VCN 618. Via a VNIC 642, thecontrol plane VCN 616 can directly communicate with, and can therebyexecute the changes, updates, or other suitable modifications toconfiguration to, resources contained in the data plane VCN 618.

In some embodiments, the control plane VCN 616 and the data plane VCN618 can be contained in the service tenancy 619. In this case, the user,or the customer, of the system may not own or operate either the controlplane VCN 616 or the data plane VCN 618. Instead, the IaaS provider mayown or operate the control plane VCN 616 and the data plane VCN 618,both of which may be contained in the service tenancy 619. Thisembodiment can enable isolation of networks that may prevent users orcustomers from interacting with other users', or other customers',resources. Also, this embodiment may allow users or customers of thesystem to store databases privately without needing to rely on publicInternet 654, which may not have a desired level of threat prevention,for storage.

In other embodiments, the LB subnet(s) 622 contained in the controlplane VCN 616 can be configured to receive a signal from the servicegateway 636. In this embodiment, the control plane VCN 616 and the dataplane VCN 618 may be configured to be called by a customer of the IaaSprovider without calling public Internet 654. Customers of the IaaSprovider may desire this embodiment since database(s) that the customersuse may be controlled by the IaaS provider and may be stored on theservice tenancy 619, which may be isolated from public Internet 654.

FIG. 7 is a block diagram 700 illustrating another example pattern of anIaaS architecture, according to at least one embodiment. Serviceoperators 702 (e.g. service operators 602 of FIG. 6 ) can becommunicatively coupled to a secure host tenancy 704 (e.g. the securehost tenancy 604 of FIG. 6 ) that can include a virtual cloud network(VCN) 706 (e.g. the VCN 606 of FIG. 6 ) and a secure host subnet 708(e.g. the secure host subnet 608 of FIG. 6 ). The VCN 706 can include alocal peering gateway (LPG) 710 (e.g. the LPG 610 of FIG. 6 ) that canbe communicatively coupled to a secure shell (SSH) VCN 712 (e.g. the SSHVCN 612 of FIG. 6 ) via an LPG 610 contained in the SSH VCN 712. The SSHVCN 712 can include an SSH subnet 714 (e.g. the SSH subnet 614 of FIG. 6), and the SSH VCN 712 can be communicatively coupled to a control planeVCN 716 (e.g. the control plane VCN 616 of FIG. 6 ) via an LPG 710contained in the control plane VCN 716. The control plane VCN 716 can becontained in a service tenancy 719 (e.g. the service tenancy 619 of FIG.6 ), and the data plane VCN 718 (e.g. the data plane VCN 618 of FIG. 6 )can be contained in a customer tenancy 721 that may be owned or operatedby users, or customers, of the system.

The control plane VCN 716 can include a control plane DMZ tier 720 (e.g.the control plane DMZ tier 620 of FIG. 6 ) that can include LB subnet(s)722 (e.g. LB subnet(s) 622 of FIG. 6 ), a control plane app tier 724(e.g. the control plane app tier 624 of FIG. 6 ) that can include appsubnet(s) 726 (e.g. app subnet(s) 626 of FIG. 6 ), a control plane datatier 728 (e.g. the control plane data tier 628 of FIG. 6 ) that caninclude database (DB) subnet(s) 730 (e.g. similar to DB subnet(s) 630 ofFIG. 6 ). The LB subnet(s) 722 contained in the control plane DMZ tier720 can be communicatively coupled to the app subnet(s) 726 contained inthe control plane app tier 724 and an Internet gateway 734 (e.g. theInternet gateway 634 of FIG. 6 ) that can be contained in the controlplane VCN 716, and the app subnet(s) 726 can be communicatively coupledto the DB subnet(s) 730 contained in the control plane data tier 728 anda service gateway 736 (e.g. the service gateway of FIG. 6 ) and anetwork address translation (NAT) gateway 738 (e.g. the NAT gateway 638of FIG. 6 ). The control plane VCN 716 can include the service gateway736 and the NAT gateway 738.

The control plane VCN 716 can include a data plane mirror app tier 740(e.g. the data plane mirror app tier 640 of FIG. 6 ) that can includeapp subnet(s) 726. The app subnet(s) 726 contained in the data planemirror app tier 740 can include a virtual network interface controller(VNIC) 742 (e.g. the VNIC of 642) that can execute a compute instance744 (e.g. similar to the compute instance 644 of FIG. 6 ). The computeinstance 744 can facilitate communication between the app subnet(s) 726of the data plane mirror app tier 740 and the app subnet(s) 726 that canbe contained in a data plane app tier 746 (e.g. the data plane app tier646 of FIG. 6 ) via the VNIC 742 contained in the data plane mirror apptier 740 and the VNIC 742 contained in the data plane app tier 746.

The Internet gateway 734 contained in the control plane VCN 716 can becommunicatively coupled to a metadata management service 752 (e.g. themetadata management service 652 of FIG. 6 ) that can be communicativelycoupled to public Internet 754 (e.g. public Internet 654 of FIG. 6 ).Public Internet 754 can be communicatively coupled to the NAT gateway738 contained in the control plane VCN 716. The service gateway 736contained in the control plane VCN 716 can be communicatively couple tocloud services 756 (e.g. cloud services 656 of FIG. 6 ).

In some examples, the data plane VCN 718 can be contained in thecustomer tenancy 721. In this case, the IaaS provider may provide thecontrol plane VCN 716 for each customer, and the IaaS provider may, foreach customer, set up a unique compute instance 744 that is contained inthe service tenancy 719. Each compute instance 744 may allowcommunication between the control plane VCN 716, contained in theservice tenancy 719, and the data plane VCN 718 that is contained in thecustomer tenancy 721. The compute instance 744 may allow resources, thatare provisioned in the control plane VCN 716 that is contained in theservice tenancy 719, to be deployed or otherwise used in the data planeVCN 718 that is contained in the customer tenancy 721.

In other examples, the customer of the IaaS provider may have databasesthat live in the customer tenancy 721. In this example, the controlplane VCN 716 can include the data plane mirror app tier 740 that caninclude app subnet(s) 726. The data plane mirror app tier 740 can residein the data plane VCN 718, but the data plane mirror app tier 740 maynot live in the data plane VCN 718. That is, the data plane mirror apptier 740 may have access to the customer tenancy 721, but the data planemirror app tier 740 may not exist in the data plane VCN 718 or be ownedor operated by the customer of the IaaS provider. The data plane mirrorapp tier 740 may be configured to make calls to the data plane VCN 718but may not be configured to make calls to any entity contained in thecontrol plane VCN 716. The customer may desire to deploy or otherwiseuse resources in the data plane VCN 718 that are provisioned in thecontrol plane VCN 716, and the data plane mirror app tier 740 canfacilitate the desired deployment, or other usage of resources, of thecustomer.

In some embodiments, the customer of the IaaS provider can apply filtersto the data plane VCN 718. In this embodiment, the customer candetermine what the data plane VCN 718 can access, and the customer mayrestrict access to public Internet 754 from the data plane VCN 718. TheIaaS provider may not be able to apply filters or otherwise controlaccess of the data plane VCN 718 to any outside networks or databases.Applying filters and controls by the customer onto the data plane VCN718, contained in the customer tenancy 721, can help isolate the dataplane VCN 718 from other customers and from public Internet 754.

In some embodiments, cloud services 756 can be called by the servicegateway 736 to access services that may not exist on public Internet754, on the control plane VCN 716, or on the data plane VCN 718. Theconnection between cloud services 756 and the control plane VCN 716 orthe data plane VCN 718 may not be live or continuous. Cloud services 756may exist on a different network owned or operated by the IaaS provider.Cloud services 756 may be configured to receive calls from the servicegateway 736 and may be configured to not receive calls from publicInternet 754. Some cloud services 756 may be isolated from other cloudservices 756, and the control plane VCN 716 may be isolated from cloudservices 756 that may not be in the same region as the control plane VCN716. For example, the control plane VCN 716 may be located in “Region1,” and cloud service “Deployment 6,” may be located in Region 1 and in“Region 2.” If a call to Deployment 6 is made by the service gateway 736contained in the control plane VCN 716 located in Region 1, the call maybe transmitted to Deployment 6 in Region 1. In this example, the controlplane VCN 716, or Deployment 6 in Region 1, may not be communicativelycoupled to, or otherwise in communication with, Deployment 6 in Region2.

FIG. 8 is a block diagram 800 illustrating another example pattern of anIaaS architecture, according to at least one embodiment. Serviceoperators 802 (e.g. service operators 602 of FIG. 6 ) can becommunicatively coupled to a secure host tenancy 804 (e.g. the securehost tenancy 604 of FIG. 6 ) that can include a virtual cloud network(VCN) 806 (e.g. the VCN 606 of FIG. 6 ) and a secure host subnet 808(e.g. the secure host subnet 608 of FIG. 6 ). The VCN 806 can include anLPG 810 (e.g. the LPG 610 of FIG. 6 ) that can be communicativelycoupled to an SSH VCN 812 (e.g. the SSH VCN 612 of FIG. 6 ) via an LPG810 contained in the SSH VCN 812. The SSH VCN 812 can include an SSHsubnet 814 (e.g. the SSH subnet 614 of FIG. 6 ), and the SSH VCN 812 canbe communicatively coupled to a control plane VCN 816 (e.g. the controlplane VCN 616 of FIG. 6 ) via an LPG 810 contained in the control planeVCN 816 and to a data plane VCN 818 (e.g. the data plane 618 of FIG. 6 )via an LPG 810 contained in the data plane VCN 818. The control planeVCN 816 and the data plane VCN 818 can be contained in a service tenancy819 (e.g. the service tenancy 619 of FIG. 6 ).

The control plane VCN 816 can include a control plane DMZ tier 820 (e.g.the control plane DMZ tier 620 of FIG. 6 ) that can include loadbalancer (LB) subnet(s) 822 (e.g. LB subnet(s) 622 of FIG. 6 ), acontrol plane app tier 824 (e.g. the control plane app tier 624 of FIG.6 ) that can include app subnet(s) 826 (e.g. similar to app subnet(s)626 of FIG. 6 ), a control plane data tier 828 (e.g. the control planedata tier 628 of FIG. 6 ) that can include DB subnet(s) 830. The LBsubnet(s) 822 contained in the control plane DMZ tier 820 can becommunicatively coupled to the app subnet(s) 826 contained in thecontrol plane app tier 824 and to an Internet gateway 834 (e.g. theInternet gateway 634 of FIG. 6 ) that can be contained in the controlplane VCN 816, and the app subnet(s) 826 can be communicatively coupledto the DB subnet(s) 830 contained in the control plane data tier 828 andto a service gateway 836 (e.g. the service gateway of FIG. 6 ) and anetwork address translation (NAT) gateway 838 (e.g. the NAT gateway 638of FIG. 6 ). The control plane VCN 816 can include the service gateway836 and the NAT gateway 838.

The data plane VCN 818 can include a data plane app tier 846 (e.g. thedata plane app tier 646 of FIG. 6 ), a data plane DMZ tier 848 (e.g. thedata plane DMZ tier 648 of FIG. 6 ), and a data plane data tier 850(e.g. the data plane data tier 650 of FIG. 6 ). The data plane DMZ tier848 can include LB subnet(s) 822 that can be communicatively coupled totrusted app subnet(s) 860 and untrusted app subnet(s) 862 of the dataplane app tier 846 and the Internet gateway 834 contained in the dataplane VCN 818. The trusted app subnet(s) 860 can be communicativelycoupled to the service gateway 836 contained in the data plane VCN 818,the NAT gateway 838 contained in the data plane VCN 818, and DBsubnet(s) 830 contained in the data plane data tier 850. The untrustedapp subnet(s) 862 can be communicatively coupled to the service gateway836 contained in the data plane VCN 818 and DB subnet(s) 830 containedin the data plane data tier 850. The data plane data tier 850 caninclude DB subnet(s) 830 that can be communicatively coupled to theservice gateway 836 contained in the data plane VCN 818.

The untrusted app subnet(s) 862 can include one or more primary VNICs864(1)-(N) that can be communicatively coupled to tenant virtualmachines (VMs) 866(1)-(N). Each tenant VM 866(1)-(N) can becommunicatively coupled to a respective app subnet 867(1)-(N) that canbe contained in respective container egress VCNs 868(1)-(N) that can becontained in respective customer tenancies 870(1)-(N). Respectivesecondary VNICs 872(1)-(N) can facilitate communication between theuntrusted app subnet(s) 862 contained in the data plane VCN 818 and theapp subnet contained in the container egress VCNs 868(1)-(N). Eachcontainer egress VCNs 868(1)-(N) can include a NAT gateway 838 that canbe communicatively coupled to public Internet 854 (e.g. public Internet654 of FIG. 6 ).

The Internet gateway 834 contained in the control plane VCN 816 andcontained in the data plane VCN 818 can be communicatively coupled to ametadata management service 852 (e.g. the metadata management system 652of FIG. 6 ) that can be communicatively coupled to public Internet 854.Public Internet 854 can be communicatively coupled to the NAT gateway838 contained in the control plane VCN 816 and contained in the dataplane VCN 818. The service gateway 836 contained in the control planeVCN 816 and contained in the data plane VCN 818 can be communicativelycouple to cloud services 856.

In some embodiments, the data plane VCN 818 can be integrated withcustomer tenancies 870. This integration can be useful or desirable forcustomers of the IaaS provider in some cases such as a case that maydesire support when executing code. The customer may provide code to runthat may be destructive, may communicate with other customer resources,or may otherwise cause undesirable effects. In response to this, theIaaS provider may determine whether to run code given to the IaaSprovider by the customer.

In some examples, the customer of the IaaS provider may grant temporarynetwork access to the IaaS provider and request a function to beattached to the data plane tier app 846. Code to run the function may beexecuted in the VMs 866(1)-(N), and the code may not be configured torun anywhere else on the data plane VCN 818. Each VM 866(1)-(N) may beconnected to one customer tenancy 870. Respective containers 871(1)-(N)contained in the VMs 866(1)-(N) may be configured to run the code. Inthis case, there can be a dual isolation (e.g., the containers871(1)-(N) running code, where the containers 871(1)-(N) may becontained in at least the VM 866(1)-(N) that are contained in theuntrusted app subnet(s) 862), which may help prevent incorrect orotherwise undesirable code from damaging the network of the IaaSprovider or from damaging a network of a different customer. Thecontainers 871(1)-(N) may be communicatively coupled to the customertenancy 870 and may be configured to transmit or receive data from thecustomer tenancy 870. The containers 871(1)-(N) may not be configured totransmit or receive data from any other entity in the data plane VCN818. Upon completion of running the code, the IaaS provider may kill orotherwise dispose of the containers 871(1)-(N).

In some embodiments, the trusted app subnet(s) 860 may run code that maybe owned or operated by the IaaS provider. In this embodiment, thetrusted app subnet(s) 860 may be communicatively coupled to the DBsubnet(s) 830 and be configured to execute CRUD operations in the DBsubnet(s) 830. The untrusted app subnet(s) 862 may be communicativelycoupled to the DB subnet(s) 830, but in this embodiment, the untrustedapp subnet(s) may be configured to execute read operations in the DBsubnet(s) 830. The containers 871(1)-(N) that can be contained in the VM866(1)-(N) of each customer and that may run code from the customer maynot be communicatively coupled with the DB subnet(s) 830.

In other embodiments, the control plane VCN 816 and the data plane VCN818 may not be directly communicatively coupled. In this embodiment,there may be no direct communication between the control plane VCN 816and the data plane VCN 818. However, communication can occur indirectlythrough at least one method. An LPG 810 may be established by the IaaSprovider that can facilitate communication between the control plane VCN816 and the data plane VCN 818. In another example, the control planeVCN 816 or the data plane VCN 818 can make a call to cloud services 856via the service gateway 836. For example, a call to cloud services 856from the control plane VCN 816 can include a request for a service thatcan communicate with the data plane VCN 818.

FIG. 9 is a block diagram 900 illustrating another example pattern of anIaaS architecture, according to at least one embodiment. Serviceoperators 902 (e.g. service operators 602 of FIG. 6 ) can becommunicatively coupled to a secure host tenancy 904 (e.g. the securehost tenancy 604 of FIG. 6 ) that can include a virtual cloud network(VCN) 906 (e.g. the VCN 606 of FIG. 6 ) and a secure host subnet 908(e.g. the secure host subnet 608 of FIG. 6 ). The VCN 906 can include anLPG 910 (e.g. the LPG 610 of FIG. 6 ) that can be communicativelycoupled to an SSH VCN 912 (e.g. the SSH VCN 612 of FIG. 6 ) via an LPG910 contained in the SSH VCN 912. The SSH VCN 912 can include an SSHsubnet 914 (e.g. the SSH subnet 614 of FIG. 6 ), and the SSH VCN 912 canbe communicatively coupled to a control plane VCN 916 (e.g. the controlplane VCN 616 of FIG. 6 ) via an LPG 910 contained in the control planeVCN 916 and to a data plane VCN 918 (e.g. the data plane 618 of FIG. 6 )via an LPG 910 contained in the data plane VCN 918. The control planeVCN 916 and the data plane VCN 918 can be contained in a service tenancy919 (e.g. the service tenancy 619 of FIG. 6 ).

The control plane VCN 916 can include a control plane DMZ tier 920 (e.g.the control plane DMZ tier 620 of FIG. 6 ) that can include LB subnet(s)922 (e.g. LB subnet(s) 622 of FIG. 6 ), a control plane app tier 924(e.g. the control plane app tier 624 of FIG. 6 ) that can include appsubnet(s) 926 (e.g. app subnet(s) 626 of FIG. 6 ), a control plane datatier 928 (e.g. the control plane data tier 628 of FIG. 6 ) that caninclude DB subnet(s) 930 (e.g. DB subnet(s) 830 of FIG. 8 ). The LBsubnet(s) 922 contained in the control plane DMZ tier 920 can becommunicatively coupled to the app subnet(s) 926 contained in thecontrol plane app tier 924 and to an Internet gateway 934 (e.g. theInternet gateway 634 of FIG. 6 ) that can be contained in the controlplane VCN 916, and the app subnet(s) 926 can be communicatively coupledto the DB subnet(s) 930 contained in the control plane data tier 928 andto a service gateway 936 (e.g. the service gateway of FIG. 6 ) and anetwork address translation (NAT) gateway 938 (e.g. the NAT gateway 638of FIG. 6 ). The control plane VCN 916 can include the service gateway936 and the NAT gateway 938.

The data plane VCN 918 can include a data plane app tier 946 (e.g. thedata plane app tier 646 of FIG. 6 ), a data plane DMZ tier 948 (e.g. thedata plane DMZ tier 648 of FIG. 6 ), and a data plane data tier 950(e.g. the data plane data tier 650 of FIG. 6 ). The data plane DMZ tier948 can include LB subnet(s) 922 that can be communicatively coupled totrusted app subnet(s) 960 (e.g. trusted app subnet(s) 860 of FIG. 8 )and untrusted app subnet(s) 962 (e.g. untrusted app subnet(s) 862 ofFIG. 8 ) of the data plane app tier 946 and the Internet gateway 934contained in the data plane VCN 918. The trusted app subnet(s) 960 canbe communicatively coupled to the service gateway 936 contained in thedata plane VCN 918, the NAT gateway 938 contained in the data plane VCN918, and DB subnet(s) 930 contained in the data plane data tier 950. Theuntrusted app subnet(s) 962 can be communicatively coupled to theservice gateway 936 contained in the data plane VCN 918 and DB subnet(s)930 contained in the data plane data tier 950. The data plane data tier950 can include DB subnet(s) 930 that can be communicatively coupled tothe service gateway 936 contained in the data plane VCN 918.

The untrusted app subnet(s) 962 can include primary VNICs 964(1)-(N)that can be communicatively coupled to tenant virtual machines (VMs)966(1)-(N) residing within the untrusted app subnet(s) 962. Each tenantVM 966(1)-(N) can run code in a respective container 967(1)-(N), and becommunicatively coupled to an app subnet 926 that can be contained in adata plane app tier 946 that can be contained in a container egress VCN968. Respective secondary VNICs 972(1)-(N) can facilitate communicationbetween the untrusted app subnet(s) 962 contained in the data plane VCN918 and the app subnet contained in the container egress VCN 968. Thecontainer egress VCN can include a NAT gateway 938 that can becommunicatively coupled to public Internet 954 (e.g. public Internet 654of FIG. 6 ).

The Internet gateway 934 contained in the control plane VCN 916 andcontained in the data plane VCN 918 can be communicatively coupled to ametadata management service 952 (e.g. the metadata management system 652of FIG. 6 ) that can be communicatively coupled to public Internet 954.Public Internet 954 can be communicatively coupled to the NAT gateway938 contained in the control plane VCN 916 and contained in the dataplane VCN 918. The service gateway 936 contained in the control planeVCN 916 and contained in the data plane VCN 918 can be communicativelycouple to cloud services 956.

In some examples, the pattern illustrated by the architecture of blockdiagram 900 of FIG. 9 may be considered an exception to the patternillustrated by the architecture of block diagram 800 of FIG. 8 and maybe desirable for a customer of the IaaS provider if the IaaS providercannot directly communicate with the customer (e.g., a disconnectedregion). The respective containers 967(1)-(N) that are contained in theVMs 966(1)-(N) for each customer can be accessed in real-time by thecustomer. The containers 967(1)-(N) may be configured to make calls torespective secondary VNICs 972(1)-(N) contained in app subnet(s) 926 ofthe data plane app tier 946 that can be contained in the containeregress VCN 968. The secondary VNICs 972(1)-(N) can transmit the calls tothe NAT gateway 938 that may transmit the calls to public Internet 954.In this example, the containers 967(1)-(N) that can be accessed inreal-time by the customer can be isolated from the control plane VCN 916and can be isolated from other entities contained in the data plane VCN918. The containers 967(1)-(N) may also be isolated from resources fromother customers.

In other examples, the customer can use the containers 967(1)-(N) tocall cloud services 956. In this example, the customer may run code inthe containers 967(1)-(N) that requests a service from cloud services956. The containers 967(1)-(N) can transmit this request to thesecondary VNICs 972(1)-(N) that can transmit the request to the NATgateway that can transmit the request to public Internet 954. PublicInternet 954 can transmit the request to LB subnet(s) 922 contained inthe control plane VCN 916 via the Internet gateway 934. In response todetermining the request is valid, the LB subnet(s) can transmit therequest to app subnet(s) 926 that can transmit the request to cloudservices 956 via the service gateway 936.

It should be appreciated that IaaS architectures 600, 700, 800, 900depicted in the figures may have other components than those depicted.Further, the embodiments shown in the figures are only some examples ofa cloud infrastructure system that may incorporate an embodiment of thedisclosure. In some other embodiments, the IaaS systems may have more orfewer components than shown in the figures, may combine two or morecomponents, or may have a different configuration or arrangement ofcomponents.

In certain embodiments, the IaaS systems described herein may include asuite of applications, middleware, and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner. Anexample of such an IaaS system is the Oracle Cloud Infrastructure (OCI)provided by the present assignee.

FIG. 10 illustrates an example computer system 1000, in which variousembodiments may be implemented. The system 1000 may be used to implementany of the computer systems described above. As shown in the figure,computer system 1000 includes a processing unit 1004 that communicateswith a number of peripheral subsystems via a bus subsystem 1002. Theseperipheral subsystems may include a processing acceleration unit 1006,an I/O subsystem 1008, a storage subsystem 1018 and a communicationssubsystem 1024. Storage subsystem 1018 includes tangiblecomputer-readable storage media 1022 and a system memory 1010.

Bus subsystem 1002 provides a mechanism for letting the variouscomponents and subsystems of computer system 1000 communicate with eachother as intended. Although bus subsystem 1002 is shown schematically asa single bus, alternative embodiments of the bus subsystem may utilizemultiple buses. Bus subsystem 1002 may be any of several types of busstructures including a memory bus or memory controller, a peripheralbus, and a local bus using any of a variety of bus architectures. Forexample, such architectures may include an Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnect (PCI) bus, which can beimplemented as a Mezzanine bus manufactured to the IEEE P1386.1standard.

Processing unit 1004, which can be implemented as one or more integratedcircuits (e.g., a conventional microprocessor or microcontroller),controls the operation of computer system 1000. One or more processorsmay be included in processing unit 1004. These processors may includesingle core or multicore processors. In certain embodiments, processingunit 1004 may be implemented as one or more independent processing units1032 and/or 1034 with single or multicore processors included in eachprocessing unit. In other embodiments, processing unit 1004 may also beimplemented as a quad-core processing unit formed by integrating twodual-core processors into a single chip.

In various embodiments, processing unit 1004 can execute a variety ofprograms in response to program code and can maintain multipleconcurrently executing programs or processes. At any given time, some orall of the program code to be executed can be resident in processor(s)1004 and/or in storage subsystem 1018. Through suitable programming,processor(s) 1004 can provide various functionalities described above.Computer system 1000 may additionally include a processing accelerationunit 1006, which can include a digital signal processor (DSP), aspecial-purpose processor, and/or the like.

I/O subsystem 1008 may include user interface input devices and userinterface output devices. User interface input devices may include akeyboard, pointing devices such as a mouse or trackball, a touchpad ortouch screen incorporated into a display, a scroll wheel, a click wheel,a dial, a button, a switch, a keypad, audio input devices with voicecommand recognition systems, microphones, and other types of inputdevices. User interface input devices may include, for example, motionsensing and/or gesture recognition devices such as the Microsoft Kinect®motion sensor that enables users to control and interact with an inputdevice, such as the Microsoft Xbox® 360 game controller, through anatural user interface using gestures and spoken commands. Userinterface input devices may also include eye gesture recognition devicessuch as the Google Glass® blink detector that detects eye activity(e.g., ‘blinking’ while taking pictures and/or making a menu selection)from users and transforms the eye gestures as input into an input device(e.g., Google Glass®). Additionally, user interface input devices mayinclude voice recognition sensing devices that enable users to interactwith voice recognition systems (e.g., Siri® navigator), through voicecommands.

User interface input devices may also include, without limitation, threedimensional (3D) mice, joysticks or pointing sticks, gamepads andgraphic tablets, and audio/visual devices such as speakers, digitalcameras, digital camcorders, portable media players, webcams, imagescanners, fingerprint scanners, barcode reader 3D scanners, 3D printers,laser rangefinders, and eye gaze tracking devices. Additionally, userinterface input devices may include, for example, medical imaging inputdevices such as computed tomography, magnetic resonance imaging,position emission tomography, medical ultrasonography devices. Userinterface input devices may also include, for example, audio inputdevices such as MIDI keyboards, digital musical instruments and thelike.

User interface output devices may include a display subsystem, indicatorlights, or non-visual displays such as audio output devices, etc. Thedisplay subsystem may be a cathode ray tube (CRT), a flat-panel device,such as that using a liquid crystal display (LCD) or plasma display, aprojection device, a touch screen, and the like. In general, use of theterm “output device” is intended to include all possible types ofdevices and mechanisms for outputting information from computer system1000 to a user or other computer. For example, user interface outputdevices may include, without limitation, a variety of display devicesthat visually convey text, graphics and audio/video information such asmonitors, printers, speakers, headphones, automotive navigation systems,plotters, voice output devices, and modems.

Computer system 1000 may comprise a storage subsystem 1018 thatcomprises software elements, shown as being currently located within asystem memory 1010. System memory 1010 may store program instructionsthat are loadable and executable on processing unit 1004, as well asdata generated during the execution of these programs.

Depending on the configuration and type of computer system 1000, systemmemory 1010 may be volatile (such as random access memory (RAM)) and/ornon-volatile (such as read-only memory (ROM), flash memory, etc.) TheRAM typically contains data and/or program modules that are immediatelyaccessible to and/or presently being operated and executed by processingunit 1004. In some implementations, system memory 1010 may includemultiple different types of memory, such as static random access memory(SRAM) or dynamic random access memory (DRAM). In some implementations,a basic input/output system (BIOS), containing the basic routines thathelp to transfer information between elements within computer system1000, such as during start-up, may typically be stored in the ROM. Byway of example, and not limitation, system memory 1010 also illustratesapplication programs 1012, which may include client applications, Webbrowsers, mid-tier applications, relational database management systems(RDBMS), etc., program data 1014, and an operating system 1016. By wayof example, operating system 1016 may include various versions ofMicrosoft Windows®, Apple Macintosh®, and/or Linux operating systems, avariety of commercially-available UNIX® or UNIX-like operating systems(including without limitation the variety of GNU/Linux operatingsystems, the Google Chrome® OS, and the like) and/or mobile operatingsystems such as iOS, Windows® Phone, Android® OS, BlackBerry® 10 OS, andPalm® OS operating systems.

Storage subsystem 1018 may also provide a tangible computer-readablestorage medium for storing the basic programming and data constructsthat provide the functionality of some embodiments. Software (programs,code modules, instructions) that when executed by a processor providethe functionality described above may be stored in storage subsystem1018. These software modules or instructions may be executed byprocessing unit 1004. Storage subsystem 1018 may also provide arepository for storing data used in accordance with the presentdisclosure.

Storage subsystem 1000 may also include a computer-readable storagemedia reader 1020 that can further be connected to computer-readablestorage media 1022. Together and, optionally, in combination with systemmemory 1010, computer-readable storage media 1022 may comprehensivelyrepresent remote, local, fixed, and/or removable storage devices plusstorage media for temporarily and/or more permanently containing,storing, transmitting, and retrieving computer-readable information.

Computer-readable storage media 1022 containing code, or portions ofcode, can also include any appropriate media known or used in the art,including storage media and communication media, such as but not limitedto, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information. This can include tangible computer-readable storagemedia such as RAM, ROM, electronically erasable programmable ROM(EEPROM), flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD), or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible computer readable media. This can also includenontangible computer-readable media, such as data signals, datatransmissions, or any other medium which can be used to transmit thedesired information and which can be accessed by computing system 1000.

By way of example, computer-readable storage media 1022 may include ahard disk drive that reads from or writes to non-removable, nonvolatilemagnetic media, a magnetic disk drive that reads from or writes to aremovable, nonvolatile magnetic disk, and an optical disk drive thatreads from or writes to a removable, nonvolatile optical disk such as aCD ROM, DVD, and Blu-Ray® disk, or other optical media.Computer-readable storage media 1022 may include, but is not limited to,Zip® drives, flash memory cards, universal serial bus (USB) flashdrives, secure digital (SD) cards, DVD disks, digital video tape, andthe like. Computer-readable storage media 1022 may also include,solid-state drives (SSD) based on non-volatile memory such asflash-memory based SSDs, enterprise flash drives, solid state ROM, andthe like, SSDs based on volatile memory such as solid state RAM, dynamicRAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, andhybrid SSDs that use a combination of DRAM and flash memory based SSDs.The disk drives and their associated computer-readable media may providenon-volatile storage of computer-readable instructions, data structures,program modules, and other data for computer system 1000.

Communications subsystem 1024 provides an interface to other computersystems and networks. Communications subsystem 1024 serves as aninterface for receiving data from and transmitting data to other systemsfrom computer system 1000. For example, communications subsystem 1024may enable computer system 1000 to connect to one or more devices viathe Internet. In some embodiments communications subsystem 1024 caninclude radio frequency (RF) transceiver components for accessingwireless voice and/or data networks (e.g., using cellular telephonetechnology, advanced data network technology, such as 3G, 4G or EDGE(enhanced data rates for global evolution), WiFi (IEEE 802.11 familystandards, or other mobile communication technologies, or anycombination thereof), global positioning system (GPS) receivercomponents, and/or other components. In some embodiments communicationssubsystem 1024 can provide wired network connectivity (e.g., Ethernet)in addition to or instead of a wireless interface.

In some embodiments, communications subsystem 1024 may also receiveinput communication in the form of structured and/or unstructured datafeeds 1026, event streams 1028, event updates 1030, and the like onbehalf of one or more users who may use computer system 1000.

By way of example, communications subsystem 1024 may be configured toreceive data feeds 1026 in real-time from users of social networksand/or other communication services such as Twitter® feeds, Facebook®updates, web feeds such as Rich Site Summary (RSS) feeds, and/orreal-time updates from one or more third party information sources.

Additionally, communications subsystem 1024 may also be configured toreceive data in the form of continuous data streams, which may includeevent streams 1028 of real-time events and/or event updates 1030, thatmay be continuous or unbounded in nature with no explicit end. Examplesof applications that generate continuous data may include, for example,sensor data applications, financial tickers, network performancemeasuring tools (e.g. network monitoring and traffic managementapplications), clickstream analysis tools, automobile trafficmonitoring, and the like.

Communications subsystem 1024 may also be configured to output thestructured and/or unstructured data feeds 1026, event streams 1028,event updates 1030, and the like to one or more databases that may be incommunication with one or more streaming data source computers coupledto computer system 1000.

Computer system 1000 can be one of various types, including a handheldportable device (e.g., an iPhone® cellular phone, an iPad® computingtablet, a PDA), a wearable device (e.g., a Google Glass® head mounteddisplay), a PC, a workstation, a mainframe, a kiosk, a server rack, orany other data processing system.

Due to the ever-changing nature of computers and networks, thedescription of computer system 1000 depicted in the figure is intendedonly as a specific example. Many other configurations having more orfewer components than the system depicted in the figure are possible.For example, customized hardware might also be used and/or particularelements might be implemented in hardware, firmware, software (includingapplets), or a combination. Further, connection to other computingdevices, such as network input/output devices, may be employed. Based onthe disclosure and teachings provided herein, a person of ordinary skillin the art will appreciate other ways and/or methods to implement thevarious embodiments.

Although specific embodiments have been described, variousmodifications, alterations, alternative constructions, and equivalentsare also encompassed within the scope of the disclosure. Embodiments arenot restricted to operation within certain specific data processingenvironments, but are free to operate within a plurality of dataprocessing environments. Additionally, although embodiments have beendescribed using a particular series of transactions and steps, it shouldbe apparent to those skilled in the art that the scope of the presentdisclosure is not limited to the described series of transactions andsteps. Various features and aspects of the above-described embodimentsmay be used individually or jointly.

Further, while embodiments have been described using a particularcombination of hardware and software, it should be recognized that othercombinations of hardware and software are also within the scope of thepresent disclosure. Embodiments may be implemented only in hardware, oronly in software, or using combinations thereof. The various processesdescribed herein can be implemented on the same processor or differentprocessors in any combination. Accordingly, where components or modulesare described as being configured to perform certain operations, suchconfiguration can be accomplished, e.g., by designing electroniccircuits to perform the operation, by programming programmableelectronic circuits (such as microprocessors) to perform the operation,or any combination thereof. Processes can communicate using a variety oftechniques including but not limited to conventional techniques forinter process communication, and different pairs of processes may usedifferent techniques, or the same pair of processes may use differenttechniques at different times.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that additions, subtractions, deletions, and other modificationsand changes may be made thereunto without departing from the broaderspirit and scope as set forth in the claims. Thus, although specificdisclosure embodiments have been described, these are not intended to belimiting. Various modifications and equivalents are within the scope ofthe following claims.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the disclosed embodiments (especially in thecontext of the following claims) are to be construed to cover both thesingular and the plural, unless otherwise indicated herein or clearlycontradicted by context. The terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (i.e., meaning“including, but not limited to,”) unless otherwise noted. The term“connected” is to be construed as partly or wholly contained within,attached to, or joined together, even if there is something intervening.Recitation of ranges of values herein are merely intended to serve as ashorthand method of referring individually to each separate valuefalling within the range, unless otherwise indicated herein and eachseparate value is incorporated into the specification as if it wereindividually recited herein. All methods described herein can beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context. The use of any and allexamples, or exemplary language (e.g., “such as”) provided herein, isintended merely to better illuminate embodiments and does not pose alimitation on the scope of the disclosure unless otherwise claimed. Nolanguage in the specification should be construed as indicating anynon-claimed element as essential to the practice of the disclosure.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is intended to be understoodwithin the context as used in general to present that an item, term,etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y,and/or Z). Thus, such disjunctive language is not generally intended to,and should not, imply that certain embodiments require at least one ofX, at least one of Y, or at least one of Z to each be present.

Preferred embodiments of this disclosure are described herein, includingthe best mode known for carrying out the disclosure. Variations of thosepreferred embodiments may become apparent to those of ordinary skill inthe art upon reading the foregoing description. Those of ordinary skillshould be able to employ such variations as appropriate and thedisclosure may be practiced otherwise than as specifically describedherein. Accordingly, this disclosure includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the disclosure unless otherwise indicated herein.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

In the foregoing specification, aspects of the disclosure are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the disclosure is not limited thereto. Variousfeatures and aspects of the above-described disclosure may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

What is claimed is:
 1. A method comprising: restarting an applicationprogramming interface (API) server with advertised IP addresses set tonew IP addresses of one or more new components to be added to a clusterconfiguration, wherein the restarting causes IP addresses of a workernode cluster service to change; detecting, by container tools associatedwith the worker node cluster service, the change in IP addresses; inresponse to detecting the change in IP addresses, determining, by eachof the container tools, whether configuration files for worker nodes ofone or more clusters of the cluster configuration need to be updated; inresponse to determining the configuration files need to be updated,attempting, by each container tool, to obtain a locking mechanism tolock respective worker nodes for updating the configuration files,wherein the locking mechanism is only obtainable by a single containertool at a time thus ensuring the configuration file of only one workernode at a time is being updated, wherein when a container tool is unableto acquire the locking mechanism, either due to a network connectivityissue or due to another container tool having the locking mechanism, thecontainer tool will retry obtaining the locking mechanism with backoff,and wherein the container tool that has the locking mechanism willensure connectivity to the API server via at least one of the advertisedIP addresses; and once connectivity is ensured to the API server,updating, by the container tool having the locking mechanism, theconfiguration file of a respective worker node.
 2. The method of claim1, wherein the one or more clusters of the cluster configuration areprovisioned with a cluster service that provides a way for anapplication deployed on a set of pods to talk to the API server using asingle endpoint.
 3. The method of claim 2, wherein the updating each ofthe worker nodes further comprises iteratively: updating, by thecontainer tool having the locking mechanism, a configuration file of thecontainer tool, restarting the container tool after updating theconfiguration file of the container tool and prior to updating theconfiguration file of the worker node, and clearing a ‘needs-migration’label from the worker node after updating the configuration file of theworker node.
 4. The method of claim 1, further comprising: updating, bythe container tool, IP addresses in other configuration files with thenew IP addresses of the one or more new components, and restarting, bythe container tool, a node agent that can register the worker node withthe APIs server.
 5. The method of claim 4, further comprising: clearinga ‘needs-migration’ label from the worker node after updating theconfiguration file of the worker node.
 6. The method of claim 1, whereinthe one or more new components comprise a service or software definedvirtual network interface card.
 7. The method of claim 1, wherein theupdating each of the worker nodes comprises iteratively: acquiring, bythe container tool, the locking mechanism for a worker node, confirming,by the container tool, connectivity from the worker node to the one ormore new components and the new IP addresses, updating, by the containertool, the configuration file of the worker node to point to the new IPaddresses, and releasing, by the container tool, the locking mechanism.8. A system comprising: one or more data processors; and anon-transitory computer readable storage medium containing instructionswhich, when executed on the one or more data processors, cause the oneor more data processors to perform actions including: restarting anapplication programming interface (API) server with advertised IPaddresses set to new IP addresses of one or more new components to beadded to a cluster configuration, wherein the restarting causes IPaddresses of a worker node cluster service to change; detecting, bycontainer tools associated with the worker node cluster service, thechange in IP addresses; in response to detecting the change in IPaddresses, determining, by each of the container tools, whetherconfiguration files for worker nodes of one or more clusters of thecluster configuration need to be updated; in response to determining theconfiguration files need to be updated, attempting, by each containertool, to obtain a locking mechanism to lock respective worker nodes forupdating the configuration files, wherein the locking mechanism is onlyobtainable by a single container tool at a time thus ensuring theconfiguration file of only one worker node at a time is being updated,wherein when a container tool is unable to acquire the lockingmechanism, either due to a network connectivity issue or due to anothercontainer tool having the locking mechanism, the container tool willretry obtaining the locking mechanism with backoff, and wherein thecontainer tool that has the locking mechanism will ensure connectivityto the API server via at least one of the advertised IP addresses; andonce connectivity is ensured to the API server, updating, by thecontainer tool having the locking mechanism, the configuration file of arespective worker node.
 9. The system of claim 8, wherein the one ormore clusters of the cluster configuration are provisioned with acluster service that provides a way for an application deployed on a setof pods to talk to the API server using a single endpoint.
 10. Thesystem of claim 9, wherein the updating each of the worker nodes furthercomprises iteratively: updating, by the container tool having thelocking mechanism, a configuration file of the container tool,restarting the container tool after updating the configuration file ofthe container tool and prior to updating the configuration file of theworker node, and clearing a ‘needs-migration’ label from the worker nodeafter updating the configuration file of the worker node.
 11. The systemof claim 8, wherein the actions further include: updating, by thecontainer tool, IP addresses in other configuration files with the newIP addresses of the one or more new components, and restarting, by thecontainer tool, a node agent that can register the worker node with theAPIs server.
 12. The system of claim 11, wherein the actions furtherinclude: clearing a ‘needs-migration’ label from the worker node afterupdating the configuration file of the worker node.
 13. The system ofclaim 8, wherein the one or more new components comprise a service orsoftware defined virtual network interface card.
 14. The system of claim8, wherein the updating each of the worker nodes comprises iteratively:acquiring, by the container tool, the locking mechanism for a workernode, confirming, by the container tool, connectivity from the workernode to the one or more new components and the new IP addresses,updating, by the container tool, the configuration file of the workernode to point to the new IP addresses, and releasing, by the containertool, the locking mechanism.
 15. A computer-program product tangiblyembodied in a non-transitory machine-readable storage medium, includinginstructions configured to cause one or more data processors to performactions including: restarting an application programming interface (API)server with advertised IP addresses set to new IP addresses of one ormore new components to be added to a cluster configuration, wherein therestarting causes IP addresses of a worker node cluster service tochange; detecting, by container tools associated with the worker nodecluster service, the change in IP addresses; in response to detectingthe change in IP addresses, determining, by each of the container tools,whether configuration files for worker nodes of one or more clusters ofthe cluster configuration need to be updated; in response to determiningthe configuration files need to be updated, attempting, by eachcontainer tool, to obtain a locking mechanism to lock respective workernodes for updating the configuration files, wherein the lockingmechanism is only obtainable by a single container tool at a time thusensuring the configuration file of only one worker node at a time isbeing updated, wherein when a container tool is unable to acquire thelocking mechanism, either due to a network connectivity issue or due toanother container tool having the locking mechanism, the container toolwill retry obtaining the locking mechanism with backoff, and wherein thecontainer tool that has the locking mechanism will ensure connectivityto the API server via at least one of the advertised IP addresses; andonce connectivity is ensured to the API server, updating, by thecontainer tool having the locking mechanism, the configuration file of arespective worker node.
 16. The computer-program product of claim 15,wherein the one or more clusters of the cluster configuration areprovisioned with a cluster service that provides a way for anapplication deployed on a set of pods to talk to the API server using asingle endpoint.
 17. The computer-program product of claim 16, whereinthe updating each of the worker nodes further comprises iteratively:updating, by the container tool having the locking mechanism, aconfiguration file of the container tool, restarting the container toolafter updating the configuration file of the container tool and prior toupdating the configuration file of the worker node, and clearing a‘needs-migration’ label from the worker node after updating theconfiguration file of the worker node.
 18. The computer-program productof claim 15, wherein the actions further include: updating, by thecontainer tool, IP addresses in other configuration files with the newIP addresses of the one or more new components, and restarting, by thecontainer tool, a node agent that can register the worker node with theAPIs server.
 19. The computer-program product of claim 18, wherein theactions further include: clearing a ‘needs-migration’ label from theworker node after updating the configuration file of the worker node.20. The computer-program product of claim 15, wherein the updating eachof the worker nodes comprises iteratively: acquiring, by the containertool, the locking mechanism for a worker node, confirming, by thecontainer tool, connectivity from the worker node to the one or more newcomponents and the new IP addresses, updating, by the container tool,the configuration file of the worker node to point to the new IPaddresses, and releasing, by the container tool, the locking mechanism.